Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df18ec1e58839aa854ac26488eeb4ddb7b78d29a1950c6c4c960505efe49f68

Tx prefix hash: f71df5475af149646763398436e2f66cbe8f990b1f4d0bd275be9d29bc66c9d6
Tx public key: e12761358a99ca85f4cd9bf65f91cd92662d8fd4f7681c236a3dea533ae818ae
Timestamp: 1631589801 Timestamp [UCT]: 2021-09-14 03:23:21 Age [y:d:h:m:s]: 03:224:12:22:00
Block: 333368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 935880 RingCT/type: yes/0
Extra: 01e12761358a99ca85f4cd9bf65f91cd92662d8fd4f7681c236a3dea533ae818ae0211000000528d0de867000000000000000000

1 output(s) for total of 48.240729872000 dcy

stealth address amount amount idx
00: 5ef3f72f134dc889257a33aa0b8bf7b94f1c98df6fe72303ccd0c36d0b7ccb4c 48.240729872000 687961 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": 333378, "vin": [ { "gen": { "height": 333368 } } ], "vout": [ { "amount": 48240729872, "target": { "key": "5ef3f72f134dc889257a33aa0b8bf7b94f1c98df6fe72303ccd0c36d0b7ccb4c" } } ], "extra": [ 1, 225, 39, 97, 53, 138, 153, 202, 133, 244, 205, 155, 246, 95, 145, 205, 146, 102, 45, 143, 212, 247, 104, 28, 35, 106, 61, 234, 83, 58, 232, 24, 174, 2, 17, 0, 0, 0, 82, 141, 13, 232, 103, 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