Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b587a94a5f83f640576026bf2ad0dcee16c78980b3587128be1fdcf0c1f6a5

Tx prefix hash: 4413c0062aef912357f2ec2dc4284ffdbce15ff687d759ea3f9db83da584096f
Tx public key: aa9ac7f687e1f885e846913d2b433da973e84d8d372bab97160161e4c12be56c
Timestamp: 1654425250 Timestamp [UCT]: 2022-06-05 10:34:10 Age [y:d:h:m:s]: 03:148:21:31:49
Block: 515973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 885827 RingCT/type: yes/0
Extra: 01aa9ac7f687e1f885e846913d2b433da973e84d8d372bab97160161e4c12be56c02110000000b5eb576c5000000000000000000

1 output(s) for total of 11.977534833000 dcy

stealth address amount amount idx
00: c6b04ffc4aa3b6a1a2dfc8674f401a9158b39314689075364aa8e39e39ba88b4 11.977534833000 943116 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": 515983, "vin": [ { "gen": { "height": 515973 } } ], "vout": [ { "amount": 11977534833, "target": { "key": "c6b04ffc4aa3b6a1a2dfc8674f401a9158b39314689075364aa8e39e39ba88b4" } } ], "extra": [ 1, 170, 154, 199, 246, 135, 225, 248, 133, 232, 70, 145, 61, 43, 67, 61, 169, 115, 232, 77, 141, 55, 43, 171, 151, 22, 1, 97, 228, 193, 43, 229, 108, 2, 17, 0, 0, 0, 11, 94, 181, 118, 197, 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