Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da001f2aa85c17c011c5c49caeba8fec3f8cb50c9d171094537f5d4c1d1a8880

Tx prefix hash: 4cb913bb1bf565f34665b3ec330a6d646566d2af03727de7481eaf01683ec7e1
Tx public key: 9bea4a18e795ee756597049256911675df56408a959be7cf9e226d3a0f47213a
Timestamp: 1628724447 Timestamp [UCT]: 2021-08-11 23:27:27 Age [y:d:h:m:s]: 03:148:15:07:04
Block: 312089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879439 RingCT/type: yes/0
Extra: 019bea4a18e795ee756597049256911675df56408a959be7cf9e226d3a0f47213a021100000001e6f80b5a000000000000000000

1 output(s) for total of 56.744014978000 dcy

stealth address amount amount idx
00: 2e3dc8bb16e7cd3a54edde561f2965cae00424177564a8292a94a6c0c41fa5ef 56.744014978000 649406 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": 312099, "vin": [ { "gen": { "height": 312089 } } ], "vout": [ { "amount": 56744014978, "target": { "key": "2e3dc8bb16e7cd3a54edde561f2965cae00424177564a8292a94a6c0c41fa5ef" } } ], "extra": [ 1, 155, 234, 74, 24, 231, 149, 238, 117, 101, 151, 4, 146, 86, 145, 22, 117, 223, 86, 64, 138, 149, 155, 231, 207, 158, 34, 109, 58, 15, 71, 33, 58, 2, 17, 0, 0, 0, 1, 230, 248, 11, 90, 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