Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f2fed06e9e3879dd9fc8a575a52d81ce3670fd6ab465625e04ad11334d76b833

Tx prefix hash: c74aa699a1035c4f3b523ce1e1f93dff2ae14ca422a77c77459d45ebc09d4c52
Tx public key: b1456d234e95f56329228f7621a07732e7474c513bf5ff3565a3c27e3a34902b
Timestamp: 1698391664 Timestamp [UCT]: 2023-10-27 07:27:44 Age [y:d:h:m:s]: 02:037:22:46:19
Block: 878627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546738 RingCT/type: yes/0
Extra: 01b1456d234e95f56329228f7621a07732e7474c513bf5ff3565a3c27e3a34902b0211000000024b8f5122000000000000000000

1 output(s) for total of 0.752911669000 dcy

stealth address amount amount idx
00: e1b16dc213fd2f6f370534644b13ddb4d16d4ace302c892e0b7d8f1b2a11743a 0.752911669000 1334089 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 878637, "vin": [ { "gen": { "height": 878627 } } ], "vout": [ { "amount": 752911669, "target": { "key": "e1b16dc213fd2f6f370534644b13ddb4d16d4ace302c892e0b7d8f1b2a11743a" } } ], "extra": [ 1, 177, 69, 109, 35, 78, 149, 245, 99, 41, 34, 143, 118, 33, 160, 119, 50, 231, 71, 76, 81, 59, 245, 255, 53, 101, 163, 194, 126, 58, 52, 144, 43, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8