Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31cf02ce71b66ec80e1109939ca36ff074f3076234e527247d7e0afa60c6da37

Tx prefix hash: 4b10fb7ba268138f8667a0e194348209982d1cebf1713fb91cc9ea863399d10a
Tx public key: 3bb5398ba7983bc69bb218e5cd6c7e7070919911a9aa26a7199d3d99a117ea67
Timestamp: 1648458861 Timestamp [UCT]: 2022-03-28 09:14:21 Age [y:d:h:m:s]: 02:350:05:48:18
Block: 468117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769649 RingCT/type: yes/0
Extra: 013bb5398ba7983bc69bb218e5cd6c7e7070919911a9aa26a7199d3d99a117ea670211000000054a0f5013000000000000000000

1 output(s) for total of 17.257018535000 dcy

stealth address amount amount idx
00: ad401aefb2c7a8554164c59c194e84e1c14e42a5ff84eb5d4153f57a3e246fd4 17.257018535000 886763 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": 468127, "vin": [ { "gen": { "height": 468117 } } ], "vout": [ { "amount": 17257018535, "target": { "key": "ad401aefb2c7a8554164c59c194e84e1c14e42a5ff84eb5d4153f57a3e246fd4" } } ], "extra": [ 1, 59, 181, 57, 139, 167, 152, 59, 198, 155, 178, 24, 229, 205, 108, 126, 112, 112, 145, 153, 17, 169, 170, 38, 167, 25, 157, 61, 153, 161, 23, 234, 103, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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