Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f43b727803f291cd5ca4e2889c98a9d4d5774c898cde5b42791eaee74a9781

Tx prefix hash: 16fb684eeba6c9db6dc7f8883405ba1f765c22f8f37568f25d3f689172f7d0d6
Tx public key: 64cea9e82e0f09cfe98548ad3eeea77fb16f686da893faea599702f2f27bdb05
Timestamp: 1670920636 Timestamp [UCT]: 2022-12-13 08:37:16 Age [y:d:h:m:s]: 02:032:09:35:53
Block: 651554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545078 RingCT/type: yes/0
Extra: 0164cea9e82e0f09cfe98548ad3eeea77fb16f686da893faea599702f2f27bdb050211000000017e406890000000000000000000

1 output(s) for total of 4.257269166000 dcy

stealth address amount amount idx
00: 84a176b4b8434ec149742f8ae7aa66b2e8967fcd4962061c63d707098c45dc42 4.257269166000 1091967 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": 651564, "vin": [ { "gen": { "height": 651554 } } ], "vout": [ { "amount": 4257269166, "target": { "key": "84a176b4b8434ec149742f8ae7aa66b2e8967fcd4962061c63d707098c45dc42" } } ], "extra": [ 1, 100, 206, 169, 232, 46, 15, 9, 207, 233, 133, 72, 173, 62, 238, 167, 127, 177, 111, 104, 109, 168, 147, 250, 234, 89, 151, 2, 242, 242, 123, 219, 5, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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