Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0584e79879baab1e327c290657eb876e0c2b2933b34ba28219d5c5168f635b

Tx prefix hash: d3c4d6acc133f2a2a0512a5de9ea6b44e7c17a46a841e852a2dda801f6b569f1
Tx public key: 0a80637b8a8b7d463b6f84d25fe47dc63dff1330c26c0c857f9260ea8da7c6d5
Timestamp: 1706744561 Timestamp [UCT]: 2024-01-31 23:42:41 Age [y:d:h:m:s]: 01:063:02:16:33
Block: 947637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306165 RingCT/type: yes/0
Extra: 010a80637b8a8b7d463b6f84d25fe47dc63dff1330c26c0c857f9260ea8da7c6d502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 421b87f7354c39bce1f967f03cb78bdd0ca5c35a3068c4edb8d63e1705964009 0.600000000000 1405995 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": 947647, "vin": [ { "gen": { "height": 947637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "421b87f7354c39bce1f967f03cb78bdd0ca5c35a3068c4edb8d63e1705964009" } } ], "extra": [ 1, 10, 128, 99, 123, 138, 139, 125, 70, 59, 111, 132, 210, 95, 228, 125, 198, 61, 255, 19, 48, 194, 108, 12, 133, 127, 146, 96, 234, 141, 167, 198, 213, 2, 17, 0, 0, 0, 2, 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