Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3715040422becbe24dde937b5d41e2a456159e389b7fad86bdbd09f5c29bf9

Tx prefix hash: b4a5f3d491d743a46c9add64a02bbfe03295326e4ec8763d5997425298f6d38e
Tx public key: 76973d3783882a2f6671f53ae2a914fd5ddb5584be6633bab45403651c1e4f73
Timestamp: 1634544702 Timestamp [UCT]: 2021-10-18 08:11:42 Age [y:d:h:m:s]: 03:189:14:49:31
Block: 355461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913285 RingCT/type: yes/0
Extra: 0176973d3783882a2f6671f53ae2a914fd5ddb5584be6633bab45403651c1e4f7302110000000a36fe6557000000000000000000

1 output(s) for total of 40.757784030000 dcy

stealth address amount amount idx
00: a54b988390e41a1b30cde80252aa52792d4bfd4d7f0d27d807b77c36e8773a73 40.757784030000 725677 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": 355471, "vin": [ { "gen": { "height": 355461 } } ], "vout": [ { "amount": 40757784030, "target": { "key": "a54b988390e41a1b30cde80252aa52792d4bfd4d7f0d27d807b77c36e8773a73" } } ], "extra": [ 1, 118, 151, 61, 55, 131, 136, 42, 47, 102, 113, 245, 58, 226, 169, 20, 253, 93, 219, 85, 132, 190, 102, 51, 186, 180, 84, 3, 101, 28, 30, 79, 115, 2, 17, 0, 0, 0, 10, 54, 254, 101, 87, 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