Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47bc772e1ca66adbf79f2921876428f3fbe32d10e7a9540f6860bf83fdea104f

Tx prefix hash: a9da87d86d053f538b725fb92701a84b32e98cc4e25269ccc3a6251bd4629d5e
Tx public key: 8e4742aeba98577eae25004c2778df24bc50b617ca3a2683d59a8b2924bfc4b3
Timestamp: 1706670389 Timestamp [UCT]: 2024-01-31 03:06:29 Age [y:d:h:m:s]: 01:107:01:44:01
Block: 947028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337623 RingCT/type: yes/0
Extra: 018e4742aeba98577eae25004c2778df24bc50b617ca3a2683d59a8b2924bfc4b30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dbc82fb07cbc85b1194f2af3890b897ab04b824424b5a72fe5b2964d5335aee 0.600000000000 1405374 of 15

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": 947038, "vin": [ { "gen": { "height": 947028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dbc82fb07cbc85b1194f2af3890b897ab04b824424b5a72fe5b2964d5335aee" } } ], "extra": [ 1, 142, 71, 66, 174, 186, 152, 87, 126, 174, 37, 0, 76, 39, 120, 223, 36, 188, 80, 182, 23, 202, 58, 38, 131, 213, 154, 139, 41, 36, 191, 196, 179, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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