Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4634457c3a8284a9fb12342b98cb2867ec974ab55e035444bdde1c03385dda2

Tx prefix hash: 559cbc0b81eade1048d2e8b312b0df03c7f40883d9eeefc005b67839f6e5abee
Tx public key: 99f360a086b4b66d03bd8d4fab2211bf758ae70a0e22cbdcea958837c1f1e052
Timestamp: 1706690777 Timestamp [UCT]: 2024-01-31 08:46:17 Age [y:d:h:m:s]: 01:277:19:11:38
Block: 947195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457337 RingCT/type: yes/0
Extra: 0199f360a086b4b66d03bd8d4fab2211bf758ae70a0e22cbdcea958837c1f1e05202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 591a9e75acb912f0e37a251f837279360bedbb0dfa92e322eb178968246b73af 0.600000000000 1405543 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": 947205, "vin": [ { "gen": { "height": 947195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "591a9e75acb912f0e37a251f837279360bedbb0dfa92e322eb178968246b73af" } } ], "extra": [ 1, 153, 243, 96, 160, 134, 180, 182, 109, 3, 189, 141, 79, 171, 34, 17, 191, 117, 138, 231, 10, 14, 34, 203, 220, 234, 149, 136, 55, 193, 241, 224, 82, 2, 17, 0, 0, 0, 4, 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