Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d86d4c9794e9f45400f6893cf1e29610c68c5b7d5cac181f1a939edf34b8ed7

Tx prefix hash: bb0e3c6519bfc2f149ec52d05e081ade87f57c8172662d7805f653fd64ce83e7
Tx public key: 29a7fd8f8e4bed745feccf9175d18edb78742d2415fe75e89fe3a75d7c1ad403
Timestamp: 1712157228 Timestamp [UCT]: 2024-04-03 15:13:48 Age [y:d:h:m:s]: 00:265:10:11:52
Block: 992512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190036 RingCT/type: yes/0
Extra: 0129a7fd8f8e4bed745feccf9175d18edb78742d2415fe75e89fe3a75d7c1ad4030211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3cf78baf3d7f0836487ba5da5eae3499fe60fe09e3d8e04dfe7ab3567aa8c09 0.600000000000 1452856 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": 992522, "vin": [ { "gen": { "height": 992512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3cf78baf3d7f0836487ba5da5eae3499fe60fe09e3d8e04dfe7ab3567aa8c09" } } ], "extra": [ 1, 41, 167, 253, 143, 142, 75, 237, 116, 95, 236, 207, 145, 117, 209, 142, 219, 120, 116, 45, 36, 21, 254, 117, 232, 159, 227, 167, 93, 124, 26, 212, 3, 2, 17, 0, 0, 0, 6, 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