Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbdd35c774018b733ad579169f3734811c90b1851994fae5e36053df1ccd24d5

Tx prefix hash: 9751e942da314f7b1a98e9f54a053059f1b42349756682e8da0feef589281218
Tx public key: f9a446c158e96684f9ccf2d9cca0e483c2a7ac3d3a0dcc9eb7bf0f86800b5fa4
Timestamp: 1652211491 Timestamp [UCT]: 2022-05-10 19:38:11 Age [y:d:h:m:s]: 02:194:08:49:41
Block: 498202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 659377 RingCT/type: yes/0
Extra: 01f9a446c158e96684f9ccf2d9cca0e483c2a7ac3d3a0dcc9eb7bf0f86800b5fa4021100000002cb8520c2000000000000000000

1 output(s) for total of 13.716716690000 dcy

stealth address amount amount idx
00: fa92ad39663cd27811a2f99305c91545db90bb4578c40076fdee08db624115dc 13.716716690000 922377 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": 498212, "vin": [ { "gen": { "height": 498202 } } ], "vout": [ { "amount": 13716716690, "target": { "key": "fa92ad39663cd27811a2f99305c91545db90bb4578c40076fdee08db624115dc" } } ], "extra": [ 1, 249, 164, 70, 193, 88, 233, 102, 132, 249, 204, 242, 217, 204, 160, 228, 131, 194, 167, 172, 61, 58, 13, 204, 158, 183, 191, 15, 134, 128, 11, 95, 164, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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