Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848cb87a65b6c5e5ab67d49f4e82b1d5ecc9bf515384aa5f8308049b975b538e

Tx prefix hash: 4bd849ff72c9585e5db27924349fe6c3b0f02d59cd678b228984c657f5d4ae71
Tx public key: d9b187bf061c1715818694fb3161d5b9f069d5693dbb0d25eb104387deba9e46
Timestamp: 1713002572 Timestamp [UCT]: 2024-04-13 10:02:52 Age [y:d:h:m:s]: 00:318:00:19:55
Block: 999530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227338 RingCT/type: yes/0
Extra: 01d9b187bf061c1715818694fb3161d5b9f069d5693dbb0d25eb104387deba9e4602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84451e95d59e6325a40972f8fd180165ec5039a6bd7e64c9fb1e08010ce104af 0.600000000000 1460010 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": 999540, "vin": [ { "gen": { "height": 999530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84451e95d59e6325a40972f8fd180165ec5039a6bd7e64c9fb1e08010ce104af" } } ], "extra": [ 1, 217, 177, 135, 191, 6, 28, 23, 21, 129, 134, 148, 251, 49, 97, 213, 185, 240, 105, 213, 105, 61, 187, 13, 37, 235, 16, 67, 135, 222, 186, 158, 70, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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