Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31b3adbc6b0b6ec35192917cac89cc072cd6c0547ef9f5e9b9bb88e6ebb944e9

Tx prefix hash: cda658858d387740f73b909e11e6f585988923b24507de55dcc740f578f00b02
Tx public key: d25ec5fda841211d3029c639cf6a41d373a83f0ab76e1cbdf6c5df0b15a03d87
Timestamp: 1673452576 Timestamp [UCT]: 2023-01-11 15:56:16 Age [y:d:h:m:s]: 02:002:10:17:16
Block: 672517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523633 RingCT/type: yes/0
Extra: 01d25ec5fda841211d3029c639cf6a41d373a83f0ab76e1cbdf6c5df0b15a03d870211000000018b7b6602000000000000000000

1 output(s) for total of 3.628039088000 dcy

stealth address amount amount idx
00: 436c21450728ed3d136055fa8588b132b0ec2041317a6bb0ce4aba6ac29e0893 3.628039088000 1114074 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": 672527, "vin": [ { "gen": { "height": 672517 } } ], "vout": [ { "amount": 3628039088, "target": { "key": "436c21450728ed3d136055fa8588b132b0ec2041317a6bb0ce4aba6ac29e0893" } } ], "extra": [ 1, 210, 94, 197, 253, 168, 65, 33, 29, 48, 41, 198, 57, 207, 106, 65, 211, 115, 168, 63, 10, 183, 110, 28, 189, 246, 197, 223, 11, 21, 160, 61, 135, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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