Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d90e1f2f510ea07fbd3e2515ae3fe2118414223c4c60d6fcf3a273c83de0f137

Tx prefix hash: f71412b7f4ed88ae0a5434f992696434e1c223928b2417559fa34ff7109ad24e
Tx public key: 5f27e179b85207591010f55e2d1397e68ff86017290ce80857fb36aa53c0218f
Timestamp: 1728803745 Timestamp [UCT]: 2024-10-13 07:15:45 Age [y:d:h:m:s]: 01:022:19:24:53
Block: 1130549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274656 RingCT/type: yes/0
Extra: 015f27e179b85207591010f55e2d1397e68ff86017290ce80857fb36aa53c0218f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354d4b93356e79c8501f3c665cb6b2c45a1aa5da36d6400dc32f36538847d1bf 0.600000000000 1613426 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": 1130559, "vin": [ { "gen": { "height": 1130549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354d4b93356e79c8501f3c665cb6b2c45a1aa5da36d6400dc32f36538847d1bf" } } ], "extra": [ 1, 95, 39, 225, 121, 184, 82, 7, 89, 16, 16, 245, 94, 45, 19, 151, 230, 143, 248, 96, 23, 41, 12, 232, 8, 87, 251, 54, 170, 83, 192, 33, 143, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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