Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcbc573f7ed3596e8ed66d4ef5b44fb529f556918c0a6ff81031c22bb2b7aea5

Tx prefix hash: f172468d78c60a613e82460e96c8c474b1acccb6cdbf3df3e96b91df00e0ff61
Tx public key: 3a3049fc0277d6b7f2046c554e5464db11e3ef7b2c7f71caa476536be7a1d465
Timestamp: 1696954411 Timestamp [UCT]: 2023-10-10 16:13:31 Age [y:d:h:m:s]: 01:036:16:17:10
Block: 866709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287415 RingCT/type: yes/0
Extra: 013a3049fc0277d6b7f2046c554e5464db11e3ef7b2c7f71caa476536be7a1d46502110000000de6d27f9c000000000000000000

1 output(s) for total of 0.824581007000 dcy

stealth address amount amount idx
00: e42923c0a3f170c8e76cb438a610889d7c58fae75be6e759accb604197e83771 0.824581007000 1321333 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": 866719, "vin": [ { "gen": { "height": 866709 } } ], "vout": [ { "amount": 824581007, "target": { "key": "e42923c0a3f170c8e76cb438a610889d7c58fae75be6e759accb604197e83771" } } ], "extra": [ 1, 58, 48, 73, 252, 2, 119, 214, 183, 242, 4, 108, 85, 78, 84, 100, 219, 17, 227, 239, 123, 44, 127, 113, 202, 164, 118, 83, 107, 231, 161, 212, 101, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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